Skip to content

Conversation

jcalvinowens
Copy link
Contributor

The chromium release tarballs contain several ancillary gitfiles like .gitignore. These files confuse devtool, and prevent its use for managing chromium patches until they are manually removed.

Since they serve no purpose, append a do_unpack stub which removes them.

Arguably, devtool should ignore ancillary gitfiles if there is no actual .git directory present: I will follow up on that upstream as well.

The chromium release tarballs contain several ancillary gitfiles like
.gitignore. These files confuse devtool, and prevent its use for
managing chromium patches until they are manually removed.

Since they serve no purpose, append a do_unpack stub which removes them.

Arguably, devtool should ignore ancillary gitfiles if there is no actual
.git directory present: I will follow up on that upstream as well.

Signed-off-by: Calvin Owens <[email protected]>
jcalvinowens added a commit to jcalvinowens/meta-browser that referenced this pull request Sep 28, 2025
@MaxIhlenfeldt
Copy link
Collaborator

Have you checked with Chromium folks whether this is something they would accept upstream, or if these files are present in the tarball by design? I believe the relevant code lives here and here.

jcalvinowens added a commit to jcalvinowens/meta-browser that referenced this pull request Oct 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants